You can use this setting to configure multi-thread processing for inbound EDI sessions that process STOWPLAN, LOADLIST, and DISCHARGELIST EDI files, or SNX, and all FLATFILE standard message types except SAUDIMANIFEST and SAUDILDP.
For example, when you set ARGOEDI008 to 8 at the EDI session level and post an inbound BAPLIE file, N4 runs as many parallel/simultaneous jobs (threads) to post the transactions in the batch for that session. The default value for ARGOEDI008 is 4.
N4 considers the value of ARGOEDI008 only when you add it to an EDI Session for any of the above message types.
Default: 4
Minimum: 1
Maximum: 24
The following table lists the message types that use the multi-thread for standard and non-standard files:
|
Message Types |
Multi-thread for Standard files |
Multi-thread for Non-Standard files |
|---|---|---|
|
ACTIVITY |
No |
No |
|
ACKNOWLEDGMENT |
No |
No |
|
APPOINTMENT |
No |
No |
|
BOOKING |
No |
No |
|
DISCHLIST |
Yes |
No |
|
HAZARD |
No |
No |
|
INVENTORY |
Yes |
Yes |
|
LOADLIST |
Yes |
No |
|
MANIFEST |
No |
No |
|
MCP VESSEL VISIT |
No |
No |
|
PREADVISE |
No |
No |
|
RAILCONSIST |
No |
No |
|
RAILORDER |
No |
No |
|
RAILWAYBILL |
Yes |
Yes |
|
RELEASE |
No |
No |
|
SAUDILDP |
No |
No |
|
SAUDIMANIFEST |
No |
No |
|
STOWPLAN |
Yes |
Yes |
|
SNX |
Yes |
Yes |
|
VESSEL ACTIVITY |
No |
No |
|
VERMAS |
No |
No |
See also ARGOBAPLIE005 (EDIPOST_THREAD_COUNT) (on page 1).
N4 does not support multi-thread processing when you post the Dishargelist EDI message with multiple units to the same BL when the setting ARGOEDI008 (EDI_POST_NUM_PARALLEL_JOBS) is greater than 1. To resolve this issue, see N4 does not support multi-thread processing for Dishcargelist EDI message with multiple units for same BL (on page 1).